-
-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update v15 #739
Update v15 #739
Conversation
Problem: The SSB-Server configures `caps` as a buffer, which breaks all connections because it's supposed to be a base64 string. Solution: Use the base64 string just like we're doing in SSB-Config.
merging, as i'm keen to upgrade |
hm, i made a new version |
yeah, seems like we're in a situation with:
oh no, shaving yaks...
vs.
|
well |
published |
Thanks @ahdinosaur |
Since #734, I am using and recommending ssb-server v15 over v16.
I would like to publish a new patch release of v15 with the following
changes:
supporting Node v12+
There are no indexing conflicts that I am aware of between v15 and v16 currently - v16 just adds ssb-private1 - so it is safe to run both of these with the same
~/.ssb
directory (not at the same time, of course). Running v15 is useful for recovering from #734.